home *** CD-ROM | disk | FTP | other *** search
- Subject: Re: ODF bug?
- Sent: 8/16/96 11:15 AM
- Received: 8/16/96 11:21 AM
- From: Henri Lamiraux, lamiraux@apple.com
- Reply-To: ODF Interest, ODF-Interest@CILabs.ORG
- To: OpenDoc Development Framework Discussion List, ODF-Interest@CILabs.
-
- >I have discovered that FW_ODPart's ReadPartInfo() is not being called when
- >a document made by may editor is inserted or dragged into an already open
- >document, say a document belonging to ODFDraw.
- >
- >This means that InternalizeFrame() does not get called and that's not good,
- >at least not if one wants to store some of the frame's data.
- >
- >This doesn't seem to be correct behavior. It seems that
- >FW_InsertPartFromFile() initiates the process within OpenDoc to insert, so
- >I suspect that it needs to do something else besides what it is doing to
- >make sure that OpenDoc calls ReadPartInfo(). Any ideas?
- >
- >Arni
- >
- >Arni F. McKinley
- >President
- >MetaMind Software, Inc.
- >Mill Valley, CA 94941
- >motion@nbn.com
- >www.nbn.com/people/minds
- >_______________________________________
- >
-
- I am not sure this is a bug in ODF. I put a debugstr in
- ODFNothing::ReadPartInfo, it is called when I open a ODFNothing document
- (that's nomal), it is not called when I dragged the document in the
- PanelEditor which is not an ODF Part.
-
- I think I know why, when you drag or insert a document the container
- recreates a brand new frame.
-
- ........................................................................
- Henri Lamiraux lamiraux@apple.com
- Apple Computer, Inc. OpenDoc(tm) Development Framework
- ........................................................................
-
-
-